User interface for displaying an item of work in a workflow context

ABSTRACT

A user interface for use in, e.g., a healthcare computing environment, for displaying an item of work in a workflow context associated with a particular resource is provided In one embodiment, the user interface includes a first workflow context display area configured to display a current workflow state of the item of work and at least one of a past workflow state and a potential future workflow state of the item of work. The user interface may further include a selectable workflow view indicator, whereby following the selectable workflow view indicator allows a user to navigate to a second workflow context display area configured to display an identity of at least one additional resource associated with the item of work and a status of the item of work as it pertains to the additional resource.

CROSS-REFERENCE TO RELATED APPLICATIONS

The application is a divisional of U.S. patent application Ser. No.11/028,263 filed Jan. 3, 2005, entitled “User Interface for Displayingan Item of Work in a Workflow Context” (Attorney Docket No. CRNI.118094)and is related by subject matter to U.S. patent application Ser. No.(unknown) filed on the same date, entitled “User Interface forDisplaying an Item of Work in a Workflow Context” (Attorney Docket No.CRNI.153581), both of which are assigned or under obligation ofassignment to the same entity as this application and incorporated inthis application by reference.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable.

TECHNICAL FIELD

The present invention relates to computing environments. Moreparticularly, embodiments of the present invention relate to a userinterface for use in, e.g., a healthcare computing environment, fordisplaying an item of work in a workflow context associated with aparticular resource or list of available resources. Further embodimentsof the present invention relate to methods in, for instance, ahealthcare computing environment, for displaying at least one item ofwork in a workflow context associated with a particular resource or listof available resources.

BACKGROUND

In modern healthcare computing environments, applications exist whichare designed to facilitate the assignment and completion of items ofwork. Items of work may include, by way of example only, a process, anorder, a step within an order process, or the like. Existingapplications generally have lists of work items from which a resource(that is, any individual, group of individuals, or machine capable ofperforming an action) selects or is presented with one or more items ofwork for which they are to take some action. Once an item of work hasbeen completed, it may be routed to another list of work items or workqueue for a different action to be performed by the same resource or adifferent resource.

In these existing applications, it is difficult for a particularresource to identify the workflow path that a work item has taken beforeit gets to them for action. It is also difficult for a particularresource to determine what actions are expected to be completed and bywhat resource. Oftentimes, items of work sit idle because a resource isunaware of how long an item of work has taken to get to them, whatactions have already been performed, and/or that work items even exist.For instance, when a physician writes a stat order, the physician oftendoes not know what resource or resources are acting upon that order andin what time frame action may be being taken. It is also unlikely that aresource will know what further actions are still needed in order forthe process (i.e., the workflow) to be considered complete.

Accordingly, a user interface which provides authorized resources theability to review past actions related to an item of work, in additionto an identity of the resource(s) that completed those past actions andthe length of time that passed prior to the item of work reaching theauthorized resource, would be desirable. Additionally, a user interfacewhich provides authorized resources the ability to identify any furtheradditional actions that are required (and by what resource(s)) in orderfor a workflow process to be considered complete would be advantageous.

BRIEF SUMMARY

Embodiments of the present invention provide a user interface for usein, e.g., a healthcare computing environment, for displaying an item ofwork in a workflow context associated with a particular resource. In oneembodiment, the user interface includes a first workflow context displayarea configured to display a current workflow state of the item of workand at least one of a past workflow state and a potential futureworkflow state of the item of work. The user interface may furtherinclude a selectable workflow view indicator, whereby following theselectable workflow view indicator allows a user to navigate to a secondworkflow context display area configured to display an identity of atleast one additional resource associated with the item of work and astatus of the item of work as it pertains to the additional resource.

In further embodiments, the user interface may include a work itemdisplay area configured to display one or more items of work to be actedupon by a first resource, wherein at least one of the one or more itemsof work comprises a selectable work item indicator. In one embodiment,following a selected one of the selectable work item indicators allows auser to navigate to a workflow context display area configured todisplay a current workflow state of the item of work associated with theselected one of the selectable work item indicators and at least one ofa past workflow state and a potential future workflow state of the itemof work associated with the selected one of the selectable work itemindicators. In another embodiment, following a selected one of theselectable work item indicators allows a user to navigate to a workflowcontext display area configured to display (1) a current workflow stateof the item of work associated with the selected one of the selectablework item indicators, (2) at least one of a past workflow state and apotential future workflow state of the item of work associated with theselected one of the selectable work item indicators, (3) an identity ofat least one additional resource associated with the item of workassociated with the selected one of the selectable work item indicators,and (4) a status of the item of work associated with the selected one ofthe selectable work item indicators as it pertains to the at least oneadditional resource.

Additional embodiments of the present invention provide methods in, forinstance, a healthcare computing environment, for displaying at leastone item of work in a workflow context associated with a particularresource. In one embodiment, the method includes receiving an item ofwork, determining a workflow for the item of work, and displaying theitem of work in the context of the determined workflow as it pertains tothe particular resource.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing the present invention;

FIG. 2 is an illustrative screen display of an exemplary user interfacehaving a first workflow context display area and a selectable workflowview indicator in accordance with an embodiment of the presentinvention;

FIG. 3 is an illustrative screen display of an exemplary user interfacehaving a second workflow context display area accessible by followingthe selectable workflow view indicator of FIG. 2;

FIG. 4 is an illustrative screen display of an exemplary user interfacehaving a work item display area, a summary display area, and a workflowcontext display area in accordance with an embodiment of the presentinvention; and

FIG. 5 is a flow chart representative of a exemplary computer programfor displaying an escalation workflow context in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention relate to a user interface for usein, e.g., a healthcare computing environment, for displaying an item ofwork in a workflow context associated with a particular resource or listof available resources. Further embodiments of the present inventionrelate to methods in, for instance, a healthcare computing environment,for displaying at least one item of work in a workflow contextassociated with a particular resource or list of available resources. Anexemplary operating environment for the present invention is describedbelow.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which the present invention maybe implemented is illustrated and designated generally as referencenumeral 20. It will be understood and appreciated by those of ordinaryskill in the art that the illustrated medical information computingsystem environment 20 is merely an example of one suitable computingenvironment and is not intended to suggest any limitation as to thescope of use or functionality of the invention. Neither should themedical information computing system environment 20 be interpreted ashaving any dependency or requirement relating to any single component orcombination of components illustrated therein.

The present invention may be operational with numerous other generalpurpose or special purpose computing system environments orconfigurations. Examples of well-known computing systems, environments,and/or configurations that may be suitable for use with the presentinvention include, by way of example only, personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. The present invention may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inlocal and/or remote computer storage media including, by way of exampleonly, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 20 includes a general purpose computingdevice in the form of a control server 22. Components of the controlserver 22 may include, without limitation, a processing unit, internalsystem memory, and a suitable system bus for coupling various systemcomponents, including database cluster 24, with the control server 22.The system bus may be any of several types of bus structures, includinga memory bus or memory controller, a peripheral bus, and a local bus,using any of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronic Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus, also known as Mezzaninebus.

The control server 22 typically includes therein, or has access to, avariety of computer readable media, for instance, database cluster 24.Computer readable media can be any available media that may be accessedby control server 22, and includes volatile and nonvolatile media, aswell as removable and nonremovable media. By way of example, and notlimitation, computer readable media may include computer storage mediaand communication media. Computer storage media may include, withoutlimitation, volatile and nonvolatile media, as well as removable andnonremovable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. In this regard, computer storage mediamay include, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVDs) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage, or other magnetic storage device, or any other medium which canbe used to store the desired information and which may be accessed bycontrol server 22. Communication media typically embodies computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 24, provide storage of computer readableinstructions, data structures, program modules, and other data forcontrol server 22.

The control server 22 may operate in a computer network 26 using logicalconnections to one or more remote computers 28. Remote computers 28 maybe located at a variety of locations in a medical environment, forexample, but not limited to, clinical laboratories, hospitals and otherinpatient settings, ambulatory settings, medical billing and financialoffices, hospital administration settings, home health careenvironments, and clinicians' offices. Clinicians may include, but arenot limited to, a treating physician or physicians, specialists such assurgeons, radiologists and cardiologists, emergency medical technicians,physicians' assistants, nurse practitioners, nurses, nurses' aides,pharmacists, dieticians, microbiologists, and the like. Remote computers28 may also be physically located in non-traditional medical careenvironments so that the entire health care community may be capable ofintegration on the network. Remote computers 28 may be personalcomputers, servers, routers, network PCs, peer devices, other commonnetwork nodes, or the like, and may include some or all of the elementsdescribed above in relation to the control server 22.

Exemplary computer networks 26 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the control server 22 may include a modem or other meansfor establishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the control server 22, in the database cluster 24, or on any of theremote computers 28. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 28. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., control server 22 and remote computers 28) may beutilized.

In operation, a user may enter commands and information into the controlserver 22 or convey the commands and information to the control server22 via one or more of the remote computers 28 through input devices,such as a keyboard, a pointing device (commonly referred to as a mouse),a trackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like. Thecontrol server 22 and/or remote computers 28 may include otherperipheral output devices, such as speakers and a printer.

Although many other internal components of the control server 22 and theremote computers 28 are not shown, those of ordinary skill in the artwill appreciate that such components and their interconnection are wellknown. Accordingly, additional details concerning the internalconstruction of the control server 22 and the remote computers 28 arenot further disclosed herein.

As previously mentioned, embodiments of the present invention relate toa user interface for displaying an item of work in a workflow contextassociated with a particular resource or list of available resources.The terms “item of work”, “work item”, “instance of work”, and “workinstance” are used interchangeably herein and refer to any itemrequiring action by one or more resources. An item of work may havevarying levels of detail ranging from a process to an order to a stepwithin an order process, or the like. As used herein the term “resource”refers to any individual (e.g., a clinician), group of individuals (forinstance, a practice group), or machine (e.g., a monitoring device orcomputer system) capable of performing an action. Additionally, the term“workflow”, as used herein, refers to the automation of a businessprocess during which documents, information, or tasks are passed fromone resource to another for action, according to a set of definedprocedural rules. The concept of workflow is known and understood bythose of ordinary skill in the art and, accordingly, is not furtherdescribed herein. By way of example only, the user interface may be usedin a healthcare computing environment for displaying an item of work ina workflow context associated with a particular clinician's assigneddaily actions.

Items of work may be generated automatically upon receipt of informationrequiring action by one or more resources or may be manually created byan authorized user. For instance, contemplate a scenario wherein a testresult is received which indicates that a potentially life-threateningcondition exists for a particular patient. Upon receipt of the testresult, a plurality of work items are likely to be generated and/orcreated notifying one or more resources that action is needed and theappropriate course of action in view of the received result is to bedetermined.

Each item of work generated is resource-specific, that is, specific tothe particular resource for which the item of work is created. Forexample, in the above-described scenario wherein it is indicated that apotentially life-threatening condition exists for a particular patientbased upon a test result, an item of work may be generated for aphysician to evaluate whether or not administration of a medication isto be ordered and another item of work may be generated for thepatient's primary care physician to review the test results forawareness of the patient's condition. As such, the user interfacedescribed herein displays the work item not only in the appropriateworkflow context, as more fully described below, but also in the contextof a particular resource, for instance, a resource accessing the userinterface.

The user interface described herein includes a workflow context displayarea configured to display a current workflow state of the item of workand at least one of a past workflow state and a potential futureworkflow state of the item of work. In this way, the item of work isdisplayed in the appropriate workflow context associated therewith. Apast workflow state may indicate a prior action or inaction by aresource that caused the work item in question to be generated orcreated. For instance, in the above-described scenario, if the work itemgenerated/created for the physician is completed upon the physician'sordering of a particular medication, another work item may be createdfor a nurse to begin administration of the ordered medication.Accordingly, the workflow context for the nurse's item of work may showa past workflow state indicating the action taken by the physician.Alternatively, if, in the above-described scenario, the physician doesnot take action on the work item within a predefined period of time(e.g., thirty minutes), the physician's item of work may beautomatically escalated by the system, resulting in a new, parallel workitem being created for the physician's supervisor indicating that actionstill needs to be taken with regard to the received test result. (Notethat in the currently described embodiment, a new work item may begenerated for the physician as well, the two work items existing inparallel until action it taken on at least one of them, as more fullydescribed below.) In this case, the workflow context for thesupervisor's item of work may show a past workflow state indicating theinaction by the physician. This type of workflow escalation is morefully described below with reference to FIG. 5.

A future workflow state indicates a potential work item that may begenerated/created if action is taken or not taken with regard to thework item in question. Future workflow states are considered “potential”as they are dependent, at least in part, on the action or inaction ofthe resource to which the item of work in question pertains. Forinstance, in the above-described scenario, if the work itemgenerated/created for the physician is completed upon the physician'sordering of a particular medication, another work item is likely to becreated for a nurse to begin administration of the ordered medication.Thus, prior to the physician's action on the work item in question, theworkflow context for the physician's item of work may show a potentialfuture workflow state indicating the nurse's potential future action.This type of workflow context may be considered a “standard” workflowcontext as it is determined according to standard procedural rules thatrepresent the best practices for the treatment of a given condition.

However, if the work item generated/created for the physician is notcompleted in a timely fashion, another work item is likely to be createdfor the physician's supervisor to take action with regard to thereceived test result. As such, an alternative workflow for thephysician's item of work may show a potential future workflow stateindicating the supervisor's potential future action. This type ofworkflow context may be considered an “exception” workflow context as itis determined based upon at least one exception to the standardprocedural rules. Exception workflow contexts are defined to captureunexpected events and direct the actions required based upon theexception. The type of exception workflow described with regard to theabove-described scenario may be considered an “escalation” workflow, andis more fully described below with reference to FIG. 5.

A determination of which future workflow state(s), and thus of theworkflow context, displayed in the workflow context display areadescribed herein is made by the system in accordance with a set ofpredefined procedural rules, as will be understood and appreciated bythose of ordinary skill in the art. Thus, the workflow context may bedetermined by a number of factors including, by way of example only, areceived test result, the criticality of a received test result, aprescribed treatment plan, an action taken by a resource associated withthe event that prompted generation/creation of the item of work inquestion, an action not taken by a resource associated with the item ofwork in question, and an availability of one or more resources who maybe associated with the item of work in question. For instance, by way ofexample only, if action has been taken with respect to the work items inall past workflow states in the workflow, the potential future workflowstate(s), and thus the workflow context, may be based on an assumptionthat the item of work related to the current workflow state will also beacted upon. However, if no action has been taken with respect to thework item of a past workflow state in the workflow, the potential futureworkflow state(s), and thus the workflow context, may be based on anassumption that the item of work related to the current workflow statewill similarly not be acted upon.

In one embodiment, the workflow context display area may be furtherconfigured to display a status indicator in association with at leastone of the current workflow state, the past workflow state(s), and thepotential future workflow state(s) within the workflow context. Thestatus indicator may be indicative of action taken or not taken withregard to a past workflow state, of time passed since generation of thework item (or time remaining to act upon the work item) with regard to acurrent workflow state, or of the fact that a work item has yet to becreated with regard to a potential future workflow state.

In one embodiment, the user interface described herein may furtherinclude an information display area configured to display detailedinformation regarding the event or events that caused the item of workin question to be generated. For instance, in the above-describedscenario, detailed information regarding the test result which promptedthe generation of the physician's item of work may be displayed in theinformation display area.

The user interface described herein may further include a summarydisplay area configured to display a summary of information pertainingto the work item in question, if desired. The summary display area mayinclude any information pertaining to the item of work. By way ofexample only, such information may include a subject line indicating theaction required by the resource/user, an identity of the patient forwhom the item of work was created, an identity of the user, and a listof additional resources for which items of work were created inassociation with the event that prompted generation/creation of the itemof work in question.

In one embodiment, the user interface of the present invention mayfurther include a selectable workflow view indicator, selection of whichmay allow a user to navigate to another workflow context display area,as more fully described below.

With reference to FIG. 2, an exemplary user interface in accordance withan embodiment of the present invention is shown and designated generallyas reference numeral 200. The user interface 200 includes a summarydisplay area 202, a workflow context display area 204, and aninformation display area 205 configured to display detailed informationregarding the event or events that caused the item of work in questionto be generated. For instance, in the illustrated scenario, a test forgram negative bacteria has come back positive for patient John Doe. Thepresence of gram negative bacteria can be a life-threatening situationand may necessitate a change in antibiotic coverage. Accordingly, uponreceiving the test result, a plurality of work items were likelycreated, one of which required a physician to endorse the result anddetermine whether or not a change in Mr. Doe's antibiotic coverage wasneeded. As such, detailed information concerning the gram negativebacteria test result, any related test results, and medicationscurrently being administered to Mr. Doe are displayed in the informationdisplay area 205.

The summary display area 202 of FIG. 2 is configured to display asummary of information pertaining to the event that promptedgeneration/creation of the item of work. In the summary display area202, the information displayed includes a subject line indicating theaction required by the user, an identity of the patient, an identity ofthe user, and a list of the resources for which items of work wereinitially created upon receipt of the test result. Also shown inassociation with each resource for which an item of work was initiallycreated is a status of the item of work associated with that resource(i.e., pending or reviewed). It will be understood and appreciated bythose of ordinary skill in the art that the information displayed in thesummary display area 202 of FIG. 2 is exemplary only and not intended tolimit the scope of the present invention in any way. Any informationpertaining to the item of work may be displayed and is intended to bewithin the scope of the present invention.

The workflow context display area 204 may be configured to display acurrent workflow state of the item of work in question, a past workflowstate of the item of work in question, and a potential future workflowstate of the item of work in question. The workflow context display area204 is further configured to display a status indicator in associationwith each of the past, current, and future workflow states. A statusindicator 208 indicates that the current workflow state of the item ofwork in question is such that the user, Nigel Cross, MD, has nineminutes remaining to endorse or otherwise take action on the receivedtest results. Shown in association with the identify of Nigel Cross, MDis an indicator 220 having a shaded figure surrounded by a thin-linedbox. This is intended to illustrate that the resource is an individualand that no action has been taken by this individual with respect to therelevant item of work.

A status indicator 206 indicates that the past workflow state of theitem of work in question is such that another resource, George Hambrect,MD, was assigned to endorse or otherwise take action on the receivedtest result and failed to act within thirty minutes, at which time thework item assigned to Dr. Hambrect was automatically escalated,resulting in a new, parallel work item being generated for Dr. Cross.(The concept of workflow escalation is more fully described below.)Shown in association with the resource identity of George Hambrect, MDis an indicator 216 having a non-shaded figure surrounded by a shadedbox. This is intended to illustrate that the required action associatedwith the corresponding work item was not completed in a timely fashionand, accordingly, an escalated work item was created as a result.

A status indicator 210 indicates that a potential future workflow stateof the item of work in question is such that if Dr. Cross fails to takeaction on the item of work in question within the remaining nine minutetime frame, the work item in question will be automatically escalated,resulting in a new, parallel work item generated for Paul Blake, MD.Simultaneously, the uncompleted work item will be forwarded to an auditlog indicating its incomplete status and a new work item generated forDr. Cross as well. In this way, after escalation, a work item exists inparallel for both resources and required action by either resource willremove both work items from their respective work item lists. That is,action by Dr. Cross on the newly generated, escalated work item willremove the parallel work item from Dr. Blake's list of work itemsrequiring action and vice versa. It will be understood and appreciatedby those of ordinary skill in the art, however, that in embodimentscontemplated by the present invention the system could escalate a singlework item, if desired.

Shown in association with the identity of Paul Blake, MD is an indicator221 having a non-shaded figure surrounded by a thin-lined box. This isintended to illustrate that the resource is an individual and that nowork items have been generated or created for this individual withrespect to the relevant item of work.

It will be understood and appreciated by those of ordinary skill in theart that the illustrated indicators 216, 220, 221 are shown by way ofexample only and are not intended to limit the scope of the presentinvention in any way.

As previously mentioned, the workflow context may be determined by anumber of factors including, by way of example only, an availability ofone or more resources associated with an item of work. In the currentlydescribed embodiment, the user interface of the present inventiondisplays information in real-time. Thus, a resource associated with anitem of work for a current or future workflow state may vary over timebased upon, for example, the clinicians and other personnel who are onthe clock at the time the user interface is being accessed.

The user interface 200 of FIG. 2 further includes a selectable workflowview indicator 212 selection of which allows a user to navigate to theworkflow context display area illustrated in FIG. 3, as more fullydescribed below.

As previously described, the user interface of the present invention mayinclude a selectable workflow view indicator, selection of which allowsa user to navigate to a second workflow context display area. The secondworkflow context display area may be configured to display additionalinformation regarding the item of work in question. By way of exampleonly, the second workflow context display area may be configured todisplay an identity of at least one additional resource for which anitem of work was generated based upon the event that prompted generationof the item of work in question and a status of that item of work as itpertains to the additional resource.

For instance, as previously described with regard to the scenariowherein it is indicated that a potentially life-threatening conditionexists for a particular patient based upon a test result, it was notedthat an item of work may be generated for a physician to evaluatewhether or not administration of a medication is to be ordered andanother item of work may be generated for the patient's primary carephysician to review the test results for awareness of the patient'scondition. In this example, the workflow context display area (e.g.,workflow context display area 204 of FIG. 2) does not indicate theaction required by, nor the action taken by, the patient's primary carephysician. While the summary display area may indicate that a work itemwas generated for the patient's primary care physician based upon theevent that prompted generation of the item of work in question, the usermay desire to view additional information regarding the action taken (ornot taken) and whether the action (or inaction) prompted any additionalwork items to be generated/created. Such information may, accordingly,be displayed in the second workflow context display area.

With reference to FIG. 3, a user interface having a second workflowcontext display area 214 is illustrated and designated generally asreference numeral 300. The user interface 300 is accessible uponselection of the workflow view indicator 212 of FIG. 2 (also shown inFIG. 3) and is configured to display the information shown in theworkflow context display area (workflow context display area 204 of FIG.2), as well as an identity of any additional resources for whom items ofwork were generated based upon the event that prompted generation of theitem of work in question and a status of those items of work as theypertain to the additional resources.

For instance, the second workflow context display area 214 includes theinformation shown in the workflow context display area 204 of FIG. 2, aswell as an indication that work items were generated for Janet Heinz,MD, Susan Hicks, RN, June Klaus, RN, Chris Collins, LPN and theDepartment of Public Health based upon the event which promptedgeneration of the item of work in question (i.e., the endorsement of thegram negative bacteria test result).

The second workflow context display area 214 further includes anindication that Janet Heinz, MD, Susan Hicks, RN, and June Klaus, RNreviewed the test result. Shown in association with the resourceidentity and status of these three resources is an indicator 218 havinga shaded figure. This is intended to illustrate that the required actionassociated with the corresponding work item has been completed.

Note that with regard to Susan Hicks, RN and June Klaus, RN, a potentialfuture workflow state is indicated as involving Eileen Flanagan, RN andTomas Ridley, MD, respectively. The status indicator for these tworesources indicates that no escalation was necessary. This is becausethe necessary action was completed before a work item was created forthese two resources. Shown in association with the identity of theseresources associated with potential future workflow states is anindicator 221 a having a non-shaded figure surrounded by a thin-linedbox similar to indicator 221 of FIG. 2. This is intended to illustratethat the resources are individuals and that no work items have beengenerated or created for these individuals with respect to the relevantitems of work.

The second workflow display area 214 also includes an indication thatChris Collins has no time limit in which to act upon the relevantgenerated work item. Shown in association with the identify of ChrisCollins, as well as the status indicator of “no time limit”, is anindicator 220 a having a shaded figure surrounded by a thin-lined boxsimilar to indicator 220 of FIG. 2. This is intended to illustrate thatthe resource is an individual and that no action has been taken by thisindividual with respect to the relevant item of work.

The second workflow display area 214 further includes an indication thatthe Department of Public Health has no time limit in which to act uponthe relevant generated work item. Shown in association with the identityof the Department of Public Health, as well as the status indicator of“no time limit”, is an indicator 222 having a shaded star-like imagesurrounded by a thin-lined box. This is intended to illustrate that theresource is a group and that no action has been taken by the group withrespect to the relevant item of work.

It will be understood and appreciated by those of ordinary skill in theart that the illustrated indicators 218, 220 a, 221 a, 222 are shown byway of example only and are not intended to limit the scope of thepresent invention in any way. It will be further understood that whilethe embodiments described herein contemplate separate and distinct userinterfaces for the first and second workflow context display areas, theareas could be unified and shown in a common display, if desired. Allsuch variations are contemplated to be within the scope hereof.

In one embodiment, the second workflow context display area 214 may bealtered by an authorized user thus changing, for example, a resourceassigned to an item of work or a time frame a resource has to respond toan item of work. As such, an authorized user may alter the workflowshown in the second workflow context display area 214, if desired.

The second workflow context display area 214 also includes a completionindicator 224, selection of which allows the user to return to the userinterface 200 of FIG. 2.

In another embodiment of the present invention, the workflow context ofa particular item of work may be accessed by a user/resource from a workitem display area configured to display one or more items of work to beacted upon by the resource. By way of example only, the work itemdisplay area of the present invention may list a plurality of workitems, each of which requires action by the resource to whom theypertain. If desired, at least one of the items of work displayed in thework item display area is a selectable work item indicator, selection ofwhich may allow a user to navigate to a workflow context display areaconfigured to display a current workflow state of the item of workassociated with the selected selectable work item indicator and at leastone of a past workflow state and a potential future workflow state ofthe item of work associated with the selected selectable work itemindicator. By way of example only, the displayed workflow contextdisplay area may be similar to workflow context display area 204 of FIG.2.

If desired, the user interface of this embodiment of the presentinvention may further include a summary display area configured todisplay a summary of information pertaining to the item of workassociated with the selected selectable work item indicator. By way ofexample only, the summary display area may be similar to the summarydisplay area 202 of FIG. 2 and may include information as described withrelation thereto.

Additionally, if desired, the user interface of this embodiment of thepresent invention may further include a selectable workflow viewindicator, selection of which allows a user to navigate to a secondworkflow context display area associated with the selected selectablework item indicator. By way of example only, the selectable workflowview indicator may be similar to the selectable workflow view indicator212 of FIG. 2 and the second workflow context display area may besimilar to the second workflow display area 214 of FIG. 3.

In another embodiment of the present invention, selection of aselectable work item indicator may allow a user to navigate directly toa workflow context display area similar to the second workflow displayarea 214 of FIG. 3.

With reference to FIG. 4, a user interface in accordance with yetanother embodiment of the present invention is illustrated anddesignated generally as reference numeral 400. The user interface 400includes a work item display area 402 configured to display one or morework items, each of which requires action by the resource to whom itpertains. If desired, at least one of the items of work displayed in thework item display area may be a selectable work item indicator,selection of which may allow a user to navigate to a workflow contextdisplay area similar to the workflow context display area 204 of FIG. 2or, if desired, to a workflow context display area similar to theworkflow context display area 214 of FIG. 3. In the illustratedembodiment, a workflow context display area 408 is shown which issimilar to the workflow context display area 214 of FIG. 3.

The user interface 400 of FIG. 4 further includes a summary display area404 configured to display a summary of information pertaining to theitem of work associated with the selected selectable work itemindicator. Though shown without detail in FIG. 4, the summary displayarea 404 may be similar to the summary display area 202 of FIG. 2 andmay include information as described with relation thereto, if desired.

The user interface 400 of FIG. 4 further includes a selectable workflowview indicator 406 selection of which allows a user to navigate to theworkflow context display area 408, if desired.

Note that in the illustrated embodiment, each of the work item displayarea 402, the summary information display area 404 and the workflowcontext display area 408 are shown on a single user interface. It willbe understood and appreciated by those of ordinary skill in the art thatthis configuration is shown by way of example only and that the workitem display area 402 the summary information display area 404 and/orthe workflow context display area 408 may be displayed independently ofone another, if desired.

As previously mentioned, one potential exception workflow which may beutilized in association with embodiments of the user interface ofpresent invention is an escalation workflow. An exemplary escalationworkflow is illustrated in the flow diagram of FIG. 5. Initially, asshown at block 510, a critical test result is received. Subsequently,the level of criticality of the test result is determined. This is shownat block 512. The level of criticality is determined based upon a rulesengine and a knowledge base taking into account such factors as, by wayof example only, the type of test result, the resources associated withthe patient for whom the test was ordered, the identity of the orderingphysician, and the like.

Subsequently, an escalation workflow is determined based upon, at leastin part, the level of criticality of the test result, the result type,and resource availability. This is shown at block 514. Subsequently orsimultaneously, a pause time (t_(i)) and a time range for at least onelevel of escalation is determined, as shown at block 516. By way ofexample only, contemplate a scenario wherein the test result indicates alife-threatening condition. In this scenario, the pause time and thetime range for each level of escalation may be relatively short (e.g.,ten minutes). However, if the test result indicates only a mildlycritical condition, the pause time and the time range for each level ofescalation may be considerably longer (e.g., one hour or one day).

Subsequently, as indicated at block 518, the resources at the firstlevel of escalation are notified of the test result and the work itemsgenerated for them with respect thereto. Next, the duration of the pausetime is waited, as indicated at block 520, and it is determined ifclinical action has been taken. This is shown at block 522. If clinicalaction has been taken the action is terminated, as indicated at block524. If, however, clinical action has not been taken, it is subsequentlydetermined whether another level of escalation is available. This isshown at block 526. If there is another level of escalation available,the resources at the next level of escalation are notified of thereceived test result and the work items generated for them with respectthereto, as indicated at block 528. Subsequently, the duration of thetime range associated with the level of escalation is waited out, and itis determined whether clinical action has been taken, as shown at block522. The process then continues to follow through this cycle until nofurther levels of escalation are available.

Once no further levels of escalation are available, all resources at alllevels of escalation are notified of the test result, as shown at block530. The duration of the pause time is subsequently waited, as indicatedat block 520, and the process continues through the indicated cycleuntil appropriate action is taken by one or more resources at which timeaction is terminated, as indicated at block 524.

It will be understood and appreciated by those of ordinary skill in theart that the above-described escalation method is described herein byway of example only and is not intended to limit the scope of thepresent invention in any way.

As can be understood, embodiments of the present invention provide auser interface for use in, e.g., a healthcare computing environment, fordisplaying an item of work in a workflow context associated with aparticular resource. Further embodiments of the present invention relateto methods in, for instance, a healthcare computing environment, fordisplaying at least one item of work in a workflow context associatedwith a particular resource.

Embodiments of the present invention provide a resource the ability tographically review the workflow path that a particular item of work hastaken, its current workflow state, and its potential future workflowstates. It also provides a resource with the identity of additionalresources that have been assigned to various workflow states related tothe particular item of work, the resources that completed those workitems, the resources that are currently assigned to other work itemsrelated to the particular process instance, and the resources that areresponsible for potential future actions. Embodiments of the presentinvention further provide a resource the ability to view the amount oftime it took for another resource to act on a particular work item orthe amount of time that has elapsed with inaction. Embodiments of thepresent invention further provide a resource the ability to easilyidentify any additional activities that are required (and by whatresources) in order for the workflow process to be considered complete.Based upon the type of work being performed, this feature can helpexpedite the completion of the workflow process and create a moreefficient and timely process.

Embodiments of the present invention provide a real-time view of workitems in process and can be utilized as a motivator to complete criticalactivities in a timely manner. In this way, embodiments of the presentinvention can help reduce medical error, improve collaboration, andimprove patient safety by making resources aware of time sensitive workitems and expedite action on those work items by prioritizing theiractions related thereto.

The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Alternative embodiments will become apparent tothose of ordinary skill in the art to which the present inventionpertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and subcombinationsare of utility and may be employed without reference to other featuresand subcombinations. This is contemplated and within the scope of theclaims.

1. A user interface embodied on at least one computer-readable medium,the user interface for displaying, in a healthcare computingenvironment, at least one item of work in a workflow context associatedwith a first resource, the user interface comprising: a work itemdisplay area configured to display one or more items of work to be actedupon by the first resource, wherein at least one of the one or moreitems of work comprises a selectable work item indicator, wherebyfollowing a selected one of the selectable work item indicators allows auser to navigate to a first workflow context display area configured todisplay a current workflow state of the item of work associated with theselected one of the selectable work item indicators and at least one ofa past workflow state and a potential future workflow state of the itemof work associated with the selected one of the selectable work itemindicators.
 2. The user interface of claim 1, wherein the first workflowcontext display area is further configured to display one of a standardworkflow context and an exception workflow context for the item of workassociated with the selected one of the selectable work item indicators.3. The user interface of claim 1, wherein the first workflow contextdisplay area is further configured to display a status indicator inassociation with at least one of the current workflow state, the pastworkflow state, and the potential future workflow state of the item ofwork associated with the selected one of the selectable work itemindicators.
 4. The user interface of claim 1, further comprising asummary display area configured to display a summary of informationpertaining to the item of work associated with the selected one of theselectable work item indicators.
 5. The user interface of claim 1,further comprising a selectable workflow view indicator, wherebyfollowing the selectable workflow view indicator allows a user tonavigate to a second workflow context display area associated with theselected one of the selectable work item indicators, the second workflowcontext display area configured to display an identity of at least oneadditional resource associated with the item of work associated with theselected one of the selectable work item indicators and a status of theitem of work associated with the selected one of the selectable workitem indicators as it pertains to the at least one additional resource.6. The user interface of claim 5, wherein the second workflow contextdisplay area is configured to be altered by an authorized user.
 7. Auser interface embodied on at least one computer-readable medium, theuser interface for displaying, in a healthcare computing environment, atleast one item of work in a workflow context associated with a firstresource, the user interface comprising: a work item display areaconfigured to display one or more items of work to be acted upon by thefirst resource, wherein at least one of the one or more items of workcomprises a selectable work item indicator, whereby following a selectedone of the selectable work item indicators allows a user to navigate toa workflow context display area configured to display a current workflowstate of the item of work associated with the selected one of theselectable work item indicators, at least one of a past workflow stateand a potential future workflow state of the item of work associatedwith the selected one of the selectable work item indicators, anidentity of at least one additional resource associated with the item ofwork associated with the selected one of the selectable work itemindicators, and a status of the item of work associated with theselected one of the selectable work item indicators as it pertains tothe at least one additional resource.